WIP: gpu-operator: test entitlement-free driver-toolkit

/test gpu-operator-commit

/test gpu-operator-commit

/test gpu-operator-commit

/test gpu-operator-commit
On Mon, Aug 30, 2021 at 7:12 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following tests failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Rerun command
ci/prow/custom 241c98b
https://github.com/openshift-psap/ci-artifacts/commit/241c98b393045bfabb6d71d43c754afdeda0386f
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-custom/1431223966172712960 /test
custom
ci/prow/gpu-operator-commit 4e39d12
https://github.com/openshift-psap/ci-artifacts/commit/4e39d12e1633925048f2368dee667713f48f45f1
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-gpu-operator-commit/1432379086394626048 /test
gpu-operator-commit
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-908523786,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQISNL2DDJG6XTQCCDVDT7O3YXANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test gpu-operator-commit

/test gpu-operator-commit

/test gpu-operator-commit

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-gpu-operator-commit/1433433104122384384/artifacts/gpu-operator-commit/presubmit-commit/artifacts/

/test gpu-operator-commit

/test ?

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Fri, Sep 3, 2021 at 4:29 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following tests failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Rerun command
ci/prow/custom 241c98b
https://github.com/openshift-psap/ci-artifacts/commit/241c98b393045bfabb6d71d43c754afdeda0386f
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-custom/1431223966172712960 /test
custom
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade 25e558a
https://github.com/openshift-psap/ci-artifacts/commit/25e558af9fb1b78739c111337858209278ccf1ca
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1433786223171735552 /test
upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-912582595,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIWGFJJUSFL57YEPPZTUADLVDANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

test succeeded, but current 4.7 and 4.8 kernels are identical
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1433833789447999488/artifacts/presubmit-gpu-operator-e2e-master-upgrade/

retesting with openshift-release config changed to test 4.8 -> 4.9
/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test images
/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Fri, Sep 3, 2021 at 9:39 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following tests failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Rerun command
ci/prow/custom 241c98b
https://github.com/openshift-psap/ci-artifacts/commit/241c98b393045bfabb6d71d43c754afdeda0386f
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-custom/1431223966172712960 /test
custom
ci/prow/images b884884
https://github.com/openshift-psap/ci-artifacts/commit/b884884fd1aa66012b3c12dd862a972ddbe06dc5
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-images/1433876578483310592 /test
images
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade b884884
https://github.com/openshift-psap/ci-artifacts/commit/b884884fd1aa66012b3c12dd862a972ddbe06dc5
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1433876650096857088 /test
upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-912767786,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIU7NIT2N4ICHWEXPWTUAEP5LANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test gpu-operator-commit

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

Test still pass after the refactoring:
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-gpu-operator-commit/1434905286358863872/artifacts/gpu-operator-commit/presubmit-commit/artifacts/
but the upgrade still doesn't change the kernel version
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1434905309633056768/artifacts/presubmit-gpu-operator-e2e-master-upgrade/2-postupgrade/artifacts/

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

testing still green
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1435214711204352000/artifacts/presubmit-gpu-operator-e2e-master-upgrade/

but something is wrong with this block:

2021-09-07T14:45:28.098Z	INFO	controllers.ClusterPolicy	DEBUG: Search for DriverToolkit DaemonSet	{"ocpVersion": "4.9.0-0.nightly-2021-09-06-055314"}
2021-09-07T14:45:28.098Z	INFO	controllers.ClusterPolicy	DEBUG: Found existing DriverToolkit DaemonSet	{"ocp versions": {"4.8.0-0.nightly-2021-09-06-042819":true,"4.9.0-0.nightly-2021-09-06-055314":true}, "image": "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:15c5a46b43b973b6ca29226cff68c0cee40d151d6b887432e708248deeed895c", "kernel": "4.18.0-305.12.1.el8_4.x86_64"}
2021-09-07T14:45:28.099Z	INFO	controllers.ClusterPolicy	DaemonSet identical, skipping update	{"DaemonSet": "nvidia-driver-daemonset", "Namespace": "gpu-operator-resources", "name": "nvidia-driver-daemonset-4.18.0-305.12.1.el8-4.x86-64"}
2021-09-07T14:45:28.099Z	INFO	controllers.ClusterPolicy	DEBUG: DaemonSet	{"LabelSelector": "app=nvidia-driver-daemonset-4.18.0-305.12.1.el8-4.x86-64"}
2021-09-07T14:45:28.099Z	INFO	controllers.ClusterPolicy	DEBUG: DaemonSet	{"NumberOfDaemonSets": 1}
2021-09-07T14:45:28.099Z	INFO	controllers.ClusterPolicy	DEBUG: DaemonSet	{"NumberUnavailable": 0}
2021-09-07T14:45:28.099Z	INFO	controllers.ClusterPolicy	DEBUG: OpenShift not in use, search for its DriverToolkit DaemonSet	{"ocpVersion": "4.8.0-0.nightly-2021-09-06-042819"}
2021-09-07T14:45:28.099Z	INFO	controllers.ClusterPolicy	DEBUG: DriverToolkit DaemonSet found	{"ocpVersion": "4.8.0-0.nightly-2021-09-06-042819", "Name": "nvidia-driver-daemonset-4.18.0-305.12.1.el8-4.x86-64", "DaemonSet.Status.DesiredNumberScheduled": 0}
2021-09-07T14:45:28.099Z	INFO	controllers.ClusterPolicy	DEBUG: DriverToolkit DaemonSet not used, delete it.	{"Name": "nvidia-driver-daemonset-4.18.0-305.12.1.el8-4.x86-64"}
2021-09-07T14:45:28.118Z	INFO	controllers.ClusterPolicy	INFO: DriverToolkit DaemonSet deleted	{"ocpVersion": "4.8.0-0.nightly-2021-09-06-042819", "Name": "nvidia-driver-daemonset-4.18.0-305.12.1.el8-4.x86-64"}

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Wed, Sep 8, 2021 at 11:51 AM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following tests failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Rerun command
ci/prow/custom 241c98b
https://github.com/openshift-psap/ci-artifacts/commit/241c98b393045bfabb6d71d43c754afdeda0386f
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-custom/1431223966172712960 /test
custom
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade b6e80bc
https://github.com/openshift-psap/ci-artifacts/commit/b6e80bc34904bd88e9d339a6c60a073da8bced9f
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1435519424307138560 /test
upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-915091709,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQITFYJ7GF4A6KFEMNRLUA4WYNANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

upgrade failed after 1h30, most likely unrelated to the GPU Operator.
2021-09-08 13:12:32,138 p=64 u=psap-ci-runner n=ansible | roles/cluster_upgrade_to_image/tasks/main.yml:32
2021-09-08 13:12:32,139 p=64 u=psap-ci-runner n=ansible | TASK: cluster_upgrade_to_image : Wait for the end of the upgrade
2021-09-08 13:12:32,139 p=64 u=psap-ci-runner n=ansible | ----- FAILED ----
2021-09-08 13:12:32,139 p=64 u=psap-ci-runner n=ansible |
2021-09-08 13:12:32,139 p=64 u=psap-ci-runner n=ansible | <command> oc get ClusterVersion/version -o jsonpath={.status.history[0].state}{"\n"}
2021-09-08 13:12:32,139 p=64 u=psap-ci-runner n=ansible |
2021-09-08 13:12:32,139 p=64 u=psap-ci-runner n=ansible | <stdout> Partial
2021-09-08 13:12:32,139 p=64 u=psap-ci-runner n=ansible | ----- FAILED ----
2021-09-08 13:12:32,141 p=64 u=psap-ci-runner n=ansible | PLAY RECAP *********************************************************************
2021-09-08 13:12:32,141 p=64 u=psap-ci-runner n=ansible | localhost                  : ok=11   changed=7    unreachable=0    failed=1    skipped=3    rescued=0    ignored=0
2021-09-08 13:12:32,141 p=64 u=psap-ci-runner n=ansible | Wednesday 08 September 2021  13:12:32 +0000 (1:30:53.007)       1:31:27.995 ***
2021-09-08 13:12:32,141 p=64 u=psap-ci-runner n=ansible | ===============================================================================
2021-09-08 13:12:32,142 p=64 u=psap-ci-runner n=ansible | cluster_upgrade_to_image --------------------------------------------- 5486.07s
2021-09-08 13:12:32,142 p=64 u=psap-ci-runner n=ansible | check_deps -------------------------------------------------------------- 1.09s
2021-09-08 13:12:32,142 p=64 u=psap-ci-runner n=ansible | gather_facts ------------------------------------------------------------ 0.80s
2021-09-08 13:12:32,142 p=64 u=psap-ci-runner n=ansible | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2021-09-08 13:12:32,142 p=64 u=psap-ci-runner n=ansible | total ---------------------------------------------------------------- 5487.97s
2021-09-08 13:12:32,142 p=64 u=psap-ci-runner n=ansible | Playbook run took 0 days, 1 hours, 31 minutes, 27 seconds

trying again
/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

hum, I almost missed it, but the testing of the driver-toolkit passed :) the deployment was successful after the upgade.
what failed is that step, I tried to switch to the usual driver toolkit:
        entitle.sh

        oc patch clusterpolicy/gpu-cluster-policy --type='json' -p='[{"op": "replace", "path": "/spec/driver/use_ocp_drivertoolkit", "value": false}]'
        validate_gpu_operator_deployment
        ./run_toolbox.py gpu-operator capture_deployment_state

and for some reason the wait timeout before the stack could be redeployed
see our driver log, still in progress
while in the gather-all, it has completed successfully

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test custom
/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test custom
/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test custom

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

+ prepare_dtk_imagestream
+ oc create imagestream driver-toolkit -n default
imagestream.image.openshift.io/driver-toolkit created
++ oc get clusterversion/version '-ojsonpath={.status.desired.version}'
+ OCP_VERSION=4.8.0-0.nightly-2021-09-15-234929
++ oc adm release info -o json quay.io/openshift-release-dev/ocp-release:4.8.0-0.nightly-2021-09-15-234929-x86_64
++ jq -r '.displayVersions."machine-os".Version'
error: image "quay.io/openshift-release-dev/ocp-release:4.8.0-0.nightly-2021-09-15-234929-x86_64" not found: manifest unknown: manifest unknown
+ RHCOS_VERSION=
+ run_finalizers

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1438485761115557888/artifacts/presubmit-gpu-operator-e2e-master-upgrade/0-preupgrade/build-log.txt
switching to lookup of the version from the node resource
/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Thu, Sep 16, 2021 at 8:09 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Rerun command
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade 4e8e992
https://github.com/openshift-psap/ci-artifacts/commit/4e8e9921b45b694ca47306f701334334278e692d
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1438540844909989888 /test
upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-921128165,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIR66DBLRI25UJ4LMITUCIXF5ANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Thu, Sep 16, 2021 at 10:03 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Rerun command
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade fd09c80
https://github.com/openshift-psap/ci-artifacts/commit/fd09c80c25ae3a0df90aa70b6fede2bd2877d4c7
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1438571797460029440 /test
upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-921205954,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQISRYRC7OU7WDCJXC73UCJEQTANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
/test custom

Hello @omertuc,
could you help me try to understand why custom passed but upgrade-presubmit-gpu-operator-e2e-master-upgrade failed in the pre-upgrade deployment stage?

both test should be doing exactly the same thing at this stage, creating a DTK DS with image

image-registry.openshift-image-registry.svc:5000/gpu-operator-resources/driver-toolkit:$RHCOS_VERSION

but the upgrade failed with
nvidia-driver-daemonset-48.84.202109161436-0-zw74c   0/1     ImagePullBackOff   0          15m   <IP_ADDRESS>   ip-10-0-145-236.ec2.internal   <none>           <none>

the image stream is prepared in this function:
prepare_dtk_imagestream() {
    TAG_NS=gpu-operator-resources

    oc create imagestream driver-toolkit -n $TAG_NS || true

    OCP_VERSION=$(oc get clusterversion/version -ojsonpath={.status.desired.version})
    DTK_IMG=$(oc adm release info $OCP_VERSION --image-for=driver-toolkit)

    RHCOS_VERSION=$(oc get nodes '-ojsonpath={range .items[*]}{.status.nodeInfo.osImage}{"\n"}{end}' | cut -d" " -f6 | uniq | head -1)

    echo "${OCP_VERSION} --> $RHCOS_VERSION --> $DTK_IMG"

    oc tag $DTK_IMG driver-toolkit:${RHCOS_VERSION} -n gpu-operator-resources
    #sleep 10

    oc get istag -n $TAG_NS > ${ARTIFACT_DIR}/imagestream.$(date +%H:%M).list
    oc get istag -n $TAG_NS -oyaml > ${ARTIFACT_DIR}/imagestream.$(date +%H:%M).yaml

    CLUSTER_RHCOS_VERSIONS=$(oc get nodes '-ojsonpath={range .items[*]}{.status.nodeInfo.osImage}{"\n"}{end}' | cut -d" " -f6 | uniq )
    echo "Versions of RHCOS in the cluster: $CLUSTER_RHCOS_VERSIONS"
}

the #sleep 10 should not have been commented out, as the commands after sometimes report nothing

logs of the custom test
logs of the upgrade test

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

Can clean up the changes from the other PR now

Can clean up the changes from the other PR now

yes, I'll just wait for the upgrade test to finish (pushing an update would stop it immediately)
FYI, I manually interfered with this CI execution:
basically I ran this command:
    DTK_RHCOS_IMG=image-registry.openshift-image-registry.svc:5000/$TAG_NS/driver-toolkit:${RHCOS_VERSION}

    MINI_POD_SPEC='{"apiVersion": "v1", "kind":"Pod","metadata":{"name":"test"},"spec":{"containers":[{"name":"cnt"}]}}'
    echo "${MINI_POD_SPEC}" | oc debug -f- --image=${DTK_RHCOS_IMG} -- echo "Image prefeched: $DTK_RHCOS_IMG"

and I think that made the Pod turn from ImagePullBackOff to working -,-
before trying this workaround, there is something different I want to try, it's to create the tag with this command:
    oc tag $DTK_IMG driver-toolkit:${RHCOS_VERSION} \
       -n gpu-operator-resources \
       --source=docker \
       --reference-policy=local

to better mimic what @dagrayvid has in the DTK PR.

upgrade failed, I'll study later how the operator behaved during the upgrade
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1438832535328002048/artifacts/presubmit-gpu-operator-e2e-master-upgrade/

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Fri, Sep 17, 2021 at 9:15 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Rerun command
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade 0830deb
https://github.com/openshift-psap/ci-artifacts/commit/0830debf27281349dbc51ad087bb3dadfe796f01
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1438890728787808256 /test
upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-922023196,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIWRMFBQRTPQ52U36C3UCOHVNANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Fri, Sep 17, 2021 at 9:42 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Rerun command
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade 0830deb
https://github.com/openshift-psap/ci-artifacts/commit/0830debf27281349dbc51ad087bb3dadfe796f01
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1438951436351180800 /test
upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-922038013,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIWJVY57RCRIWGNYWZTUCOK27ANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Sat, Sep 18, 2021 at 12:13 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade 0830deb
https://github.com/openshift-psap/ci-artifacts/commit/0830debf27281349dbc51ad087bb3dadfe796f01
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1439116504153985024
true /test upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-922253758,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIQKZX36DBEIZSMHOQLUCRQ5RANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Sat, Sep 18, 2021 at 4:37 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade e44d43f
https://github.com/openshift-psap/ci-artifacts/commit/e44d43ff5bc55ab5aac98c86130eae4493f27a25
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1439182413740642304
true /test upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-922305910,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIXFQ4QVC6DKMYERRG3UCSP3LANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Sat, Sep 18, 2021 at 9:18 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade e44d43f
https://github.com/openshift-psap/ci-artifacts/commit/e44d43ff5bc55ab5aac98c86130eae4493f27a25
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1439278849106907136
true /test upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-922359568,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIUT3D2GWOOQC5CQKLDUCTQXDANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Sat, Sep 18, 2021 at 11:53 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade fc116d1
https://github.com/openshift-psap/ci-artifacts/commit/fc116d1b53380af425bb3bc90274275e166d46cb
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1439325322104279040
true /test upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-922379010,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIUVHJSP72V5QS7RYFTUCUC6HANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test custom

/test custom

/test custom

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Mon, Sep 20, 2021 at 6:05 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade 7c2da4a
https://github.com/openshift-psap/ci-artifacts/commit/7c2da4a6d17d1ffcbff4f8a0a416ec49bcaaf068
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1439962625445203968
true /test upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-923065429,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIWNUM5YQTK42SASR4TUC5LVPANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
/test custom

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Tue, Sep 21, 2021 at 7:45 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade 42ba6a3
https://github.com/openshift-psap/ci-artifacts/commit/42ba6a3f839ce7d782c4519e0683e1d90bc51eb6
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1440318233956585472
true /test upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-924215417,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIXWSVPLPJBPISU5LPLUDDABZANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Wed, Sep 22, 2021 at 6:28 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade 42ba6a3
https://github.com/openshift-psap/ci-artifacts/commit/42ba6a3f839ce7d782c4519e0683e1d90bc51eb6
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1440659632379924480
true /test upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-925089588,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIVLJCCXFSIFMTA5WH3UDH7YVANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
/test ?

/test 4.10-gpu-operator-e2e

/test 4.10-gpu-operator-e2e

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Thu, Sep 23, 2021 at 11:55 AM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following tests failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade 2c0cb51
https://github.com/openshift-psap/ci-artifacts/commit/2c0cb5147ab617fb1e25eea0627a7ecdb15e3e15
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1440723312358461440
true /test upgrade-presubmit-gpu-operator-e2e-master-upgrade
ci/prow/4.10-gpu-operator-e2e 8f5afe3
https://github.com/openshift-psap/ci-artifacts/commit/8f5afe35270982e28afda8830236630c2f6aeb07
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-4.10-gpu-operator-e2e/1440974954878210048
true /test 4.10-gpu-operator-e2e
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-925665728,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQISKLKBOTI7QD7BA2N3UDL2R5ANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test 4.10-gpu-operator-e2e

force pushed to unbreak the 4.10 CI
/test 4.10-gpu-operator-e2e
/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test 4.10-gpu-operator-e2e
/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Thu, Sep 23, 2021 at 5:45 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following tests failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/4.10-gpu-operator-e2e 7188659
https://github.com/openshift-psap/ci-artifacts/commit/718865952f3da05299f50a272b8715941fdcc89e
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-4.10-gpu-operator-e2e/1441014137307009024
true /test 4.10-gpu-operator-e2e
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade 7188659
https://github.com/openshift-psap/ci-artifacts/commit/718865952f3da05299f50a272b8715941fdcc89e
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1441014137340563456
true /test upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-925935316,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIUOGMNCITTFAHQV25LUDNDSTANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test 4.10-gpu-operator-e2e
/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

test failed during cluster bring up
/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
and retry:
/test 4.10-gpu-operator-e2e

error: build error: failed to pull image: After retrying 2 times, Pull image still failed due to error: initializing source docker://registry.fedoraproject.org/fedora:latest: pinging container registry registry.fedoraproject.org: Get "https://registry.fedoraproject.org/v2/": dial tcp <IP_ADDRESS>:443: i/o timeout

both tests failed because of this ^^^
/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
/test 4.10-gpu-operator-e2e

Fedora 34 - x86_64                               28 MB/s |  74 MB     00:02
Fedora 34 openh264 (From Cisco) - x86_64        460  B/s | 2.5 kB     00:05
Fedora Modular 34 - x86_64                       10 kB/s | 3.3 kB     00:00
Errors during downloading metadata for repository 'fedora-modular':
  - Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-34&arch=x86_64 (IP: <IP_ADDRESS>)
  - Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-34&arch=x86_64&countme=1 (IP: <IP_ADDRESS>)

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1442461784328900608/artifacts/presubmit-gpu-operator-e2e-master-upgrade/0-preupgrade/artifacts/003__gpu_operator__bundle_from_commit/helper-image-builder.log
fedora repos down?

I added a commit that should solve the ImagePullBackOff that we were seeing.
It was caused by a race condition between the population of the ServiceAccount secrets and the DaemonSet->Pod creation.
/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
/test 4.10-gpu-operator-e2e

I updated the gpu_operator_wait_deployment to wait longer for DCGM Pod to come online
/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
/test 4.10-gpu-operator-e2e

/test 4.10-gpu-operator-e2e

/test 4.10-gpu-operator-e2e
On Thu, Sep 30, 2021 at 12:11 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following tests failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/4.10-gpu-operator-e2e bc94ef1
https://github.com/openshift-psap/ci-artifacts/commit/bc94ef1d987b87460a541b5264d6489c2d3ba9ab
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-4.10-gpu-operator-e2e/1443505459028824064
true /test 4.10-gpu-operator-e2e
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade bc94ef1
https://github.com/openshift-psap/ci-artifacts/commit/bc94ef1d987b87460a541b5264d6489c2d3ba9ab
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1443505367681077248
true /test upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-931184813,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIUI2LWRLX3CPGKKZIDUEQZVDANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test 4.10-gpu-operator-e2e
/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Thu, Sep 30, 2021 at 1:17 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following tests failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade bc94ef1
https://github.com/openshift-psap/ci-artifacts/commit/bc94ef1d987b87460a541b5264d6489c2d3ba9ab
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1443505367681077248
true /test upgrade-presubmit-gpu-operator-e2e-master-upgrade
ci/prow/4.10-gpu-operator-e2e 7a55712
https://github.com/openshift-psap/ci-artifacts/commit/7a557123689a13397b583bb323c74ada66f8e577
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-4.10-gpu-operator-e2e/1443520807929122816
true /test 4.10-gpu-operator-e2e
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-931228654,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIQFN7V246POPIKNCCDUERBLVANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test 4.10-gpu-operator-e2e

/test 4.10-gpu-operator-e2e

/test 4.10-gpu-operator-e2e

/test 4.10-gpu-operator-e2e
/test gpu-operator-e2e

/test gpu-operator-e2e

ci/prow/gpu-operator-e2e passed \o/
this is the first version where the DTK lives as a side-car container, along with NVIDIA driver container.
/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
/test 4.10-gpu-operator-e2e

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
/test 4.10-gpu-operator-e2e

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
/test 4.10-gpu-operator-e2e

/test 4.10-gpu-operator-e2e
/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Mon, Oct 4, 2021 at 5:27 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/4.10-gpu-operator-e2e bee8ce6
https://github.com/openshift-psap/ci-artifacts/commit/bee8ce686c434b89078e42ef1bad33d69e912be3
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-4.10-gpu-operator-e2e/1445032416015028224
true /test 4.10-gpu-operator-e2e
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-933597863,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIVXYAU4JO7ZTUKVYU3UFHBURANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Tue, Oct 5, 2021 at 12:01 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade 9472df2
https://github.com/openshift-psap/ci-artifacts/commit/9472df2e878a1ac078d71fccd6c5c2f93b7ab796
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1445283958639038464
true /test upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-934257959,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIQB2SU7LE6QU7HLM7TUFLEINANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Sat, Oct 9, 2021 at 10:02 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade 298e4be
https://github.com/openshift-psap/ci-artifacts/commit/298e4becefa4a995ae632134bece6019d7be29dd
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1446911735704326144
true /test upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-939354518,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIWKLGJCAUHJTCSKPK3UGCNT5ANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
On Sun, Oct 10, 2021 at 2:35 AM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/upgrade-presubmit-gpu-operator-e2e-master-upgrade ad56351
https://github.com/openshift-psap/ci-artifacts/commit/ad563512085e158fc01c58447b3a421821a378e8
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/241/pull-ci-openshift-psap-ci-artifacts-master-upgrade-presubmit-gpu-operator-e2e-master-upgrade/1446979803084230656
true /test upgrade-presubmit-gpu-operator-e2e-master-upgrade
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=241.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/241#issuecomment-939382734,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIQF4X3SK7HJOKMPBWDUGDNWVANCNFSM5B6ANIFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade

/test upgrade-presubmit-gpu-operator-e2e-master-upgrade
/test 4.9-gpu-operator-e2e
/test 4.10-gpu-operator-e2e

/test 4.9-gpu-operator-e2e

/test 4.9-gpu-operator-e2e

/test 4.10-gpu-operator-e2e

/test gpu-operator-e2e

ci/prow/4.8-presubmit-gpu-operator-e2e-master-upgrade-to-4-9

/test 4.8-presubmit-gpu-operator-e2e-master-upgrade-to-4-9

/test 4.8-presubmit-gpu-operator-e2e-master-upgrade-to-4-9
/test 4.7-presubmit-gpu-operator-e2e-master-upgrade-to-4-8


Implement layout margins relative arrangement.

layout margins relative arrangement
This PR implements the layout margins relative arrangement feature. It defines two new properties:
@property(nonatomic) UIEdgeInsets layoutMargins;
@property(nonatomic, getter=isLayoutMarginsRelativeArrangement) BOOL layoutMarginsRelativeArrangement;

The first one just defines the missing layoutMargins property on iOS7.
The second one switches the layout relative to margins.
I also added some buttons to visualize the feature in the example App.
bonus

In the process of developing this feature I also solved a small bug with the center alignment: because it didn't define any constraints relative to the edges of the stackView, the content views could easily overflow the stackView boundaries. This was fixed.

I also added a background view to help visualize the margins. Now that the stackView's backing layer is a CATransformLayer we could not set a backgroundColor on it to help visualize the layout. I fixed this by placing a background view behind the stackView and constraining it to have the same size and center of the stackView.

I'm using this fork now, and it's very nice and works as intended. :+1:

This looks great!!, Sorry for the later reply, Can you add a couple of test cases to verify the margin alignment? Otherwise I will add them my self in the weekend.

Yes, I’ll try to add them in the weekend.

Any updates? I'm anxious to try this fork with the latest updates to master :grin:

Hey, Me too :D.
I had little time this weekend but I definitely want to merge this asap.
I will try to add some specs tomorrow in case @cabeca cannot add them.

Sorry about the delay. I added the missing tests to the project.

Great, this addition is super cool!
I will merge this branch by hand since I want to fix the failing test on iOS 7

Merged! Thanks!


[Fix] Add pom file for paimon-web-ui module.

Purpose
close: https://github.com/apache/incubator-paimon-webui/issues/175
The paimon-web-ui module does not add a pom file, causing the module to not be found when the project is compiled. This PR adds pom file for paimon-web-ui module.

Since the paimon-web-ui-new module was renamed to paimon-web-ui last time, no pom file was added, which resulted in failure to compile, so ci failed to pass. After adding the pom file to this PR, this problem can be fixed.


Major improvement in bookbinding, edits in pageborder.

In this commit, I updated BookBinding effect with the addition of PageBorder and here are some of the examples:


options removed from Money 6.13.5

Seems that this gem isn't compatible with the latest money version (6.13.5)
NameError: undefined local variable or method `options' for #<Money::RatesStore::StoreWithHistoricalDataSupport:0x000055ad13572018>
Did you mean?  @options
/home/circleci/mrclean/vendor/bundle/ruby/2.6.0/gems/eu_central_bank-1.4.2/lib/money/rates_store/store_with_historical_data_support.rb:23:in `transaction'
/home/circleci/mrclean/vendor/bundle/ruby/2.6.0/gems/eu_central_bank-1.4.2/lib/eu_central_bank.rb:179:in `update_parsed_rates'
/home/circleci/mrclean/vendor/bundle/ruby/2.6.0/gems/eu_central_bank-1.4.2/lib/eu_central_bank.rb:29:in `update_rates'
/home/circleci/mrclean/app/better_now/accounting/ecb_bank.rb:25:in `update_rates'
/home/circleci/mrclean/app/better_now/accounting/ecb_bank.rb:20:in `initialize'
/home/circleci/mrclean/app/better_now/accounting/ecb_bank.rb:12:in `new'
/home/circleci/mrclean/app/better_now/accounting/ecb_bank.rb:12:in `setup'
/home/circleci/mrclean/config/initializers/money_exchange_bank.rb:4:in `<top (********)>'

This looks like the change that causes the problem: https://github.com/RubyMoney/money/pull/898/files#diff-70409fffc5690f30fb7495abab7a7dbfL103

https://github.com/RubyMoney/eu_central_bank/blob/b413b1c3dfbbc0146cbaa4de935eed8e8fc6fbd3/lib/money/rates_store/store_with_historical_data_support.rb#L13-L33 is horribly broken.
    # Wraps block execution in a thread-safe transaction
    def transaction(force_sync = false, &block)
      # Ruby 1.9.3 does not support @mutex.owned?
      if @mutex.respond_to?(:owned?)
        force_sync = false if @mutex.locked? && @mutex.owned?
      else
        # If we allowed this in Ruby 1.9.3, it might possibly cause recursive
        # locking within the same thread.
        force_sync = false
      end
      if !force_sync && (@in_transaction || options[:without_mutex])
        block.call self
      else
        @mutex.synchronize do
          @in_transaction = true
          result = block.call
          @in_transaction = false
          result
        end
      end
    end

As soon as @in_transaction = true is set, any other thread can enter in the block without synchronisation.
If result = block.call raises an exception, @in_transaction = false is never called.

@ioquatix It would be helpful to know if you found any alternative.

@shailesh-kalamkar An alternative to what?

@ioquatix An alternative to this gem which is using the same API. Basically, would like to know how did you overcome the issue?
Thanks.

@shailesh-kalamkar https://github.com/ioquatix/latinum

Thank you so much.

Sorry about this, 6.13.6 is now available that include a fix for this regression

https://github.com/RubyMoney/money/issues/900#issuecomment-562070633

Sorry again, just published eu_central_bank 1.5.0 that should finally fix this and rely on a thread-safe implementation of the superclass for synchronisation

@antstorm great work!


Define Project structure

I think we can close this issue. Issue description is not concrete enough, and it is already archived in our Project Backlog.


Does anyone know PVAnet? How to configure its CRelu structure using mxnet

The pvanet is proposed in https://github.com/sanghoon/pva-faster-rcnn
It use caffe to train and infer.
Like title, I want to know how to implement the CRelu structure.
The structure is that
Conv->bn->concat(bn, -bn)->scale->Relu
How to configure it?
Should I use fix_gamma parameter?

how to transfer caffe scale layer to mxnet symbol?

Hi, have you finished PVAnet on mxnet? I am interested on it.

This issue is closed due to lack of activity in the last 90 days. Feel free to ping me to reopen if this is still an active issue. Thanks!
Also, do please check out our forum (and Chinese version) for general "how-to" questions.


Add Namespace Patching to RBAC good practice

Updating the RBAC Good Practices guide to include information on Patch operations against Namespaces being a security risk.

/hold
OK to unhold once the reviews I mentioned in https://github.com/kubernetes/website/pull/45664#discussion_r1539282769 are done.

/hold cancel
Thanks @IanColdwater

I'm going to use my maintainer access to fix just the style nits - see https://github.com/kubernetes/website/pull/45664/files#r1539294992

Thanks so much, @smarticu5, for the research here and the followup to call attention to this surprising behavior.
/lgtm
/honk

Appreciate this is closed now, thanks all. I've added a PoC using a minimal role and rolebinding to my own repo (https://github.com/smarticu5/kubernetes_manifests/tree/main/pocs/namespace-labelling) for future reference.


Typo and grammar fixes

This fixes typo and grammar in some of the Alert components and the ECommerce header sample.

Thanks @sorxrob✨🤓


Feature request: Show both translation result and original text when doing a file translation

Hi, thanks for building such a powerful translation plugin, I think it's more powerful than those in obsidian plugin market.
I just realize it's more convenient when reading translation and original text in one file, because most translations are not very accurate and we need to see original text to get the meaning.
Will you consider to add a feature, when doing a file translation, show translation result and original text paragraph by paragraph, for example:
when we translate an English file to Chinese, the file finally show like this:

Obsidian is a powerful and extensible knowledge base that works on top of your local folder of plain text files.
Obsidian 是一个强大且可扩展的知识库它适用于纯文本文件的本地文件夹。
 Your second brain should work the same.
人脑是非线性的：我们总是从一个想法跳到另一个想法。你的第二个大脑应该同样工作。
In Obsidian, making and following connections is frictionless.
在 Obsidian 中，建立和跟随连接是无摩擦的。像园丁一样照顾你的笔记；在一天结束时，坐下来惊叹于您自己的知识图谱。

I am not sure this is a feature most people will need or not but it's definitely a difficult and complicated feature. I don't know obsidian plugin system can realize this or not, if not, you can just pass my request.

Thank you for your great feedback!
This is definitely something I could (and would like to) implement, though it will take me a while to get to - as I'm currently swamped with other work.
Whenever I do get started on this feature, I'll share some of the design ideas here so you can give your input on it!

Wow! So happy you are interested about this feature. You are amazing!


Replace for loop with iterators

Hi! I've figured out how to replace a loop with iterators here :)
Not sure that this is an improvement, but my experience tells me that "functional" approach, while less obvious, is more robust.
Feel free to merge or close!

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

Ah yeah I feel like the gymnastics with Result -> Option<Result> may decrease readability here a bit, so I'm gonna close for now. Good to always explore though!

Ok, or maybe I'll just automatically hit the merge button...


beer and coffee for the HIE team

It came up again in a recent discussion that we complain a lot about tooling in the Haskell community, but we also rarely express our gratitude when things actually get better.
I'm personally extremely happy that HIE exists. The feature set is great, the installation story is slowly getting nicer, the recent GSoC was super solid, and people are friendly and helpful when responding to issues.
In that reddit thread we came up with buying our favourite IDE tools a couple of beers (or coffees). The maintainer of vscode-ghc-simple has paid his forward to you, which would entitle you to a total of 8. The only problem is: how to I get those to you? For contributors in the EU I can suggest Revolut, otherwise bank transfers could work. PayPal is also an option. Maybe beerpay.io?
If you think it's too much hassle, then I will donate the sum (~40$ ?) to a charity of your choice.

Thanks for the gesture.
I am contemplating putting some sort of structure in place for HIE, like using https://opencollective.com or similar.
But it is just an idle thought at the moment.

I like the general idea of projects like HIE getting a bit of monetary inflow. Opencollective is very cool.
Some questions that come to mind: Will it be satisfying even if the amounts are pretty small? Let's say you get 50.- per month, that's nice, but more pocket money and less developer pay. Do you have things in mind that could be improved, accelerated or paid for with money? Better CI? Bounties? Travel costs to a conference or hackathon?
A good example to look at is fody, which does some nudging to get corporate users to contribute. But I don't know what lessons HIE can use from their model.

Consider signing up for  https://github.com/sponsors


feat: update to use laravel/serializable-closure package

This allows supporting PHP 8.1, and is required for us to continue using this package with Box, as 4.x of opis/closure requires FFI, which afaik isn't wanted for Box. Happy to make any changes if required. 👍🏻
It looks like Travis doesn't yet support PHP 8.1 (unless it's hardcoded to 8.1.0) 🤷🏻
Also, looks like the quotes were changed in error messages as part of PHP 8.0 (see https://github.com/php/php-src/pull/5590), so I've updated the testUnserializableClassStaticMethod() test to cover this.

NOTE: This can be rebased after https://github.com/amphp/parallel-functions/pull/30 and https://github.com/amphp/parallel-functions/pull/31 have been merged. 👍🏻

Are there any compatibility concerns or is it fine to release this as v1.1.0?

@kelunik AFAICS this should not introduce any API changes. I would not recommend a patch release still but bumping the minor version looks fine

Yeah, we usually also increase the minor version on PHP version increments I think, independent from the dependency change.

I'll rebase this and resolve the issues mentioned hopefully tomorrow morning. 👍🏻 Cheers.

@kelunik / @theofidry, that should now all be sorted. 🥳 Let me know if there's anything else required. 👍🏻

Thanks! I really like how focused the PR is now. 😊

Yeah, much nicer to have each component update in separate PRs. 👍🏻

On a side note @kelunik, it looks like Travis CI is no longer running on the repository. Would you be interested in me opening a PR to migrate to GitHub Actions? Or, if not, I guess it might be worth re-enabling Travis CI. 👍🏻

I know, already thought about asking you to update that as well, but just did it myself. :smile:

I've tagged v1.1.0 now. :tada:

Thanks a lot!

Thank you!

This breaks GrumPHP (see https://github.com/phpro/grumphp/issues/957)


How can I do a bar chart with two bars with the same label?

I was reading the docs but I could not find a way to get this result,
is there any way to display a chart like this one?
https://raw.githubusercontent.com/Abhinandan-Kushwaha/react-native-gifted-charts/0480eb7c4e05fca9a82fc76b04c7507fc83a002a/demos/barPairs.svg
https://raw.githubusercontent.com/Abhinandan-Kushwaha/react-native-gifted-charts/0480eb7c4e05fca9a82fc76b04c7507fc83a002a/demos/barPairs.svg

Hi Alejandro Vega, the updated version 0.1.6 is live now!
Also, I have added the code for the requested chart in the docs, it's at the bottom of the Bar chart section. Hope it helps you 😊

Hi Alejandro Vega, the updated version 0.1.6 is live now! Also, I have added the code for the requested chart in the docs, it's at the bottom of the Bar chart section. Hope it helps you 😊

its working for line chart only
Please update for bar chart


Fix undefined error in server tree data source (#12616)

Fixes https://github.com/microsoft/azuredatastudio/issues/12615

Pull Request Test Coverage Report for Build 271223330

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 38.915%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/services/objectExplorer/browser/serverTreeDataSource.ts
0
1
0.0%

Totals

Change from base Build 269438546:
0.01%

Covered Lines:
19242

Relevant Lines:
45114

💛  - Coveralls

Merging as per DRI meeting


Can not represent 0xfffff... as 64 bit integer

Godot version:
3.2
OS/device including version:
Windows
Issue description:

The project still running, but keep appear this error in debug

Can you upload a minimal reproduction project in which this error occurs?

Hex can only be only represented as unsigned int, but in code hex_to_int64 return int64 which can overflow when putting to it value bigger that 2^63
https://github.com/godotengine/godot/blob/1eb424ec9549bdd086dfb54c847d107519be73d9/core/ustring.h#L248-L251

Can anyone still reproduce this bug in Godot 3.2.3 or any later release?

Hi guys !
I'm having the exact same problem when using Ncryp class from: https://github.com/johngirvin/godot-ncrypt
The class producing the problem is the script NCrypt.gd: https://github.com/johngirvin/godot-ncrypt/blob/master/project/NCrypt/NCrypt.gd
Is still present in Godot 3.3.2.stable

I can reproduce this on master with the following script:
extends Node
func _ready():
	# Any number larger than `0x8fff_ffff_ffff_ffff` seems to trigger this.
    print(str(0xffff_ffff_ffff_ffff))

What would be the correct way to solve this? GDScript does not have an unsigned 64-bit integer type (or unsigned integer types in the first place).

The bug still exists on 3.4.3.

There is no way to solve this without adding an unsigned integer type. Godot will already print an error for numbers it can't represent, so this is handled properly.


In DataGrid when using column selector, the first time a column is hidden the grid is scrolled down

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
There's a DataGrid. The data grid has a toolbar. The toolbar has a column selector. The first time a column visibility is changed is hidden, the page is scrolled down. The second time onwards, the scrolling doesn't happen.
Expected Behavior 🤔
For the grid not to scroll down.
Steps to Reproduce 🕹
It's exactly the same as in the docs: https://material-ui.com/components/data-grid/columns/#column-selector
The first time a column visibility is changed is hidden the page will scroll down.
Also, if the column visibility is changed, and then the grid is sorted or filtered, and then a column visibility is changed again, it will scroll again.

https://github.com/mui-org/material-ui-x/issues/1148


A question on VCN performance in Table 1

I find an inconsistency in describing the running time of VCN in Table 1 between the arxiv paper  : 0.18 and the official paper: 0.03.
Could you let me know the exact runtime?
Thanks!

The running time of VCN in the official paper may be wrong. We later notice that its runtime is claimed to be 0.18 in the KITTI website.

The running time of VCN in the official paper may be wrong. We later notice that its runtime is claimed to be 0.18 in the KITTI website.

Thanks for the clarification.


[e2e] Results of e2e tests in github actions for iptables backend and ipv6 family.

There are some test cases failing for iptables with ipv6 family.
Please check the below link for references.
https://github.com/kubernetes-sigs/kpng/runs/4362502966?check_suite_focus=true

As we have less no of issues in each of the backends due to lot of issues fixed, closing this issue. We can open new issues for each failures now.


What are the advantages of using a large language model to implement a virtual honeypot?

The virtual honeypot based on LLM is a fantastic idea. However, the deployment cost of large language models is relatively high. From an engineering perspective, what are the practical benefits of using a large language model as a honeypot? Or, looking at it from the perspective of writing a research paper, how can I convince reviewers that using a large language model to implement a virtual honeypot is a great solution? Can the high interactivity and a closer approximation to real devices brought by large language models compensate for their significant performance overhead?

Hi @StarrYMSkY,
Nice to meet you :)

However, the deployment cost of large language models is relatively high -> Used as a production honeypot in a cluster or internal network, the number of attacks approaches zero, but used as a research honeypot the costs are high due to the large number of attacks.
What are the practical benefits of using a large language model as a honeypot? -> Works like high interaction honeypot! But is a low interaction honeypot: more secure, you don't have to supervise it.

Here you find a very interesting paper: https://arxiv.org/pdf/2301.03771.pdf
I hope I have answered all your questions.
Thanks for your time
Mario


升级2.0.0版本启动后一直报错

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description
升级2.0.0版本后，启动后一直报错
Ⅱ. Describe what happened

Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)

xxx
xxx
xxx

Minimal yet complete reproducer code (or URL to code):
Ⅴ. Anything else we need to know?
Ⅵ. Environment:

JDK version(e.g. java -version):
Seata client/server version:
Database version:
OS(e.g. uname -a):
Others:

Please try to check if there is a network problem at this address

Please try to check if there is a network problem at this address

内网服务之间都是通的，client端都能注册到server端，而且好像也不影响使用，这个错是个warn级别的，您说的网络问题是指该机器能否访问外网吗

ping -s 128 -i 0.2 ip
类似这样在seata-server侧去ping一下网络状况，还有这个异常在你的client如果出现非优雅下线时也是会出现的，异常信息就是字面意思
Similar to this on the seata-server side to ping the network status, there is also this exception in your client if there is a non-graceful downtime will also appear, the exception information is literally


Some minor code cleanup in the tests

This is mainly some code cleanup in the tests:

Fix the order of the arguments of assertEquals (or replaces it with assertThat if it is already used in the TestCase)
Add a missing override annotation
Replace the deprecated org.apache.commons.io.Charsets with java.nio.charset.StandardCharsets (this is fixed in org.dspace.discovery.FullTextContentStreams, too)
Remove member variables that are already declared in the AbstractUnitTest
Replace deprecated (in hibernate-5.2) createSQLQuery with createNativeQuery (this is replaced in org.dspace.eperson.dao.impl.GroupDAOImpl, too)
Add a charset to IOUtils.copy, because using the default charset is deprecated
Make an inner class static, because it does not reference the enclosing class. This fixes a warning during compilation.

Merging as this is at +2, and is primarily Test refactors (which are verified by Travis CI).  There's only a few minor API refactors, but both seem very obvious fixes.


"giving up" while configuring

How to reproduce: start M8M with no config file. Open the admin wizard. Leave everything here.
After a while, M8M will "give up" due to lack of stratum traffic.

I have not been able to test the latest updates, I can not find the executable.
Thanks

It's ok because I filled this while testing the release. Version 801 is up now.


chore: refactor run schema

Following is the current schema:
// If defines the conditions required to verify the
// presence of, absence of, equals to & other checks
// against one or more resources observed in the cluster
type If struct {
	// OR-ing or AND-ing of conditions
	IfOperator IfOperator `json:"operator,omitempty"`

	// List of conditions that get executed as part of
	// if operation
	IfConditions []IfCondition `json:"conditions,omitempty"`
}

// IfCondition to match, filter, verify a kubernetes resource.
type IfCondition struct {
	// Selector to filter one or more resources that are expected
	// to be present in the cluster
	ResourceSelector metac.ResourceSelector `json:"resourceSelector,omitempty"`

	// ResourceOperator refers to the operation that gets executed to
	// the selected resources
	//
	// Defaults to 'Exists'
	ResourceOperator ResourceOperator `json:"operator,omitempty"`

	// Count comes into effect when operator is related to count
	// e.g. EqualsCount, GreaterThanEqualTo, LessThanEqualTo.
	Count *int `json:"count,omitempty"`
}

Following is the proposed schema
// ResourceCheck defines the conditions required to verify the
// presence of, absence of, equals to & other checks
// against one or more resources observed in the cluster
type ResourceCheck struct {
	// OR-ing or AND-ing of conditions
	SelectConditionOperator ResourceSelectConditionOperator `json:"selectConditionOperator,omitempty"`

	// List of conditions that get executed as part of
	// if operation
	SelectConditions []ResourceSelectCondition `json:"selectConditions,omitempty"`
}

// ResourceSelectCondition to match, filter, verify a kubernetes resource.
type ResourceSelectCondition struct {
	// Selector to filter one or more resources that are expected
	// to be present in the cluster
	Selector metac.ResourceSelector `json:"resourceSelector,omitempty"`

	// Operator refers to the operation that gets executed to
	// the selected resources
	//
	// Defaults to 'Exists'
	Operator ResourceSelectorOperator `json:"selectOperator,omitempty"`

	// Count comes into effect when operator is related to count
	// e.g. EqualsCount, GreaterThanEqualTo, LessThanEqualTo.
	Count *int `json:"count,omitempty"`
}

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Decouple in-memory client from persist module

Purpose
Fixes:
Examples
Checklist

[ ] Linked to an issue
[ ] Updated the specification
[ ] Updated the changelog
[ ] Added tests
[ ] Checked native-image compatibility

@kaneeldias please review


Patch for /Books.ListMyLibrary/Books.ListMyLibrary.csproj

solo salvarlo

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 4 Sep 2014 at 1:10
Attachments:

Books.ListMyLibrary.csproj.patch

clean up question is almost 2 years old no more info was supplied


Handle newlines

Fix for https://github.com/jbowens/jBBCode/issues/31
Hardens tag options parsing a bit so that neither newlines nor extra spaces break anything. eg.
This contains a [
        url=http://jbbcode.com   ]url[/url] which uses an option, and has a newline in the tag.

:+1:

might need to rebase off master but lgtm

Removed newline and sync'ed with master.

:+1:


Doesn't restore all logs and messages

when i check my gmail all backups are there(untill today), but when i try to restore it only some of it got restored(after a long time counting from zero to 12K).
btw only mesages and logs older than 09/06/2014 are restored.
and i have sms backup + shows 12k messages and logs.

I have the same issue trying to restore after flashing marshmallow on my Nexus 5.

there are some restore improvements done in the current beta beta (#586), maybe try with this version
https://github.com/jberkel/sms-backup-plus/releases/tag/1.5.11-BETA2

Great it worked. Thanks a lot!

@jberkel actually it seems to works but the dates are off ... Everything is good in Gmail but the dates and time are not good in Hangouts after Restoring.
Also when you do a Backup I can see that the time is not good in the app.

Same issue even with latest release https://github.com/jberkel/sms-backup-plus/releases/tag/1.5.11-BETA3

@gablabelle how far out at the timestamps? Could this be a matter of timezone slippage? Are the timestamps wrong by a whole number of hours, and off by no more than ±1 day?

@Ham3D and @kakawait are you still having this problem?

@kurahaupo i’ve had about 5 phones since that nexus 5 lol ... Sorry i don’t remember how this ended for me.


add categories to Cargo.toml

@homunkulus r+

:pushpin: Commit aca8c9a has been approved by japaric

:hourglass: Testing commit aca8c9a with merge aca8c9a...

:sunny: Test successful - status-appveyor, status-travis
Approved by: japaric
Pushing aca8c9a6e8a2d9f41b5b20299042e0c13e37d092 to master...


Bumping go version to 1.21.1

Bumping go version to 1.21.1

These tests are failing because we do not allow the Workflow files to be changed when we are doing end-to-end tests.


Tool to figure out if top 1-2 layers are “dirt” and then ignore them if prompt suggests so

One problem with geology descriptions sometimes is the top layer or two is very young poorly lithified stuff not very in common with the “outcrops” or regional geology. Hence, you might sometimes want to ignore it or concentrate on it.
where there is nothing but young stuff around, so old passive margins with long standing current deposition (gulf coast), you might want to include it.
Anywhere there is other bedrock around, you’re going to probably want to skip it by default unless prompted otherwise.
Anything that is 0 thickness would qualify. Anything that is very young, so <5milliom years old would qualify. Sometimes, you might skip anything 0-10? Not sure where a general cut off might be?
If the second layer is much older, 20Ma, then probably jump to that one if thickness <50m?
how might this be worded such that prompt language is considered?

figured out an easier approach


Extend on.change event to specific items

Hi all
I have a on.changed event setup, which hides a html element once the carousel item has changed, working good so far. The problem I'm struggling with, is that I only want to hide #select in the footer when item 2 and 3 are show, then re show when unselected.
How can I narrow this down so the event only fires when these certain item are in focus, become active, instead of all the items?
  $('footer').find('#select').css("display", "none");
}); ```

Wondering if we can use the below some how:
> var items     = event.item.count;     // Number of items
> var item      = event.item.index;     // Position of the current item

Any suggestion, much appreciated thanks.

http://jsfiddle.net/av0bkbzx/

Barry

Fixed it :)
Here is the code. Not sure if a better way is possible, or if I need a closing else statment, things work good either way. If this can help anybody else trying to perform certain events on their own carousel.
    if( event.item.index === 1 || event.item.index === 2 || event.item.index === 5 ) {
      $('footer').find('#select').css("display", "none");
    }
    else if( event.item.index === 0 || event.item.index === 3 || event.item.index === 4 ) {
      $('footer').find('#select').css("display", "block");
    }
  });```

http://jsfiddle.net/av0bkbzx/1/

Barry


[BUG] Instantly crashes for some reason

Describe the bug
Before upgrading, I was on <IP_ADDRESS> and it was working fine. But after the DelayOTA, all apps I try to run don’t work, and I made sure I was using JIT. I even factory reset my iPad but it did not work. My device is iPad Pro 11” 4th generation.
Instructions to reproduce

Upgrade iOS to 16.5
LiveContainer doesn’t work

What version of LiveContainer are you using?
Version 1.0-release (main/67a3696)
Other info
No response

Maybe this is caused by additional factors. Which version is this application tested on?

Maybe this is caused by additional factors. Which version is this application tested on?
Edit: Forgot to mention there is no error whatsoever…

Please send app analytics data

Please send app analytics data

How can I find this?

Spotlight search > type “Analytics” > Analytics Data > send the most recent LiveContainer ips

Spotlight search

Hey there! After searching and retrying multiple times (attempting to open apps and crashing), the LiveContainer analytics data isn’t created.

Also I just noticed, whenever I run something and it crashes, my iPad becomes unbearably hot. Perhaps it does run but it crashes and runs indefinitely?

The recent commit fixed the issue! Thanks for making such amazing apps available to us, it means a lot.