-
-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Smoke Tests #86
Add Smoke Tests #86
Conversation
Thank you for creating a pull request! |
run tests |
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
run tests |
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
run tests |
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
run tests |
🟢 PR TESTER RESULT 🟢✅ All pipelines passed! ✅ |
a748aa8
to
f7e7702
Compare
run tests |
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
run tests |
🟢 PR TESTER RESULT 🟢✅ All pipelines passed! ✅ |
@sophia-guo Is this ready for review now? |
run tests |
Signed-off-by: Sophia Guo <sophia.gwf@gmail.com>
@M-Davies - are you good to proceed with this PR? It shows you as requesting a change, have all your requests been met? |
IMHO, enableTests could just as well be called enableAQATests. The smoke tests are different, they are not part of the AQA tests, they are checking the tarball was built with the correct features enabled, and correct version information and metadata has been be produced. There could then be a enableSmokeTests option, because one may want smoke tests but not AQA tests... I don't want us to get bogged down in this however, it is more important that we are running these then whether some person kicking off build pipelines is monkeying with settings. So the proposal to
is fine by me. |
Signed-off-by: Sophia Guo <sophia.gwf@gmail.com>
@M-Davies updated. |
run tests (assuming the PR tester does not pick up any issues missed, I'll be happy to approve this) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR tester is down due to the current jenkins instability. There's nothing I can see in the code that would indicate it would fail so I'm happy to approve this and submit a test pipeline after merge
If you are ready to merge this @M-Davies please do so (I do not believe @sophia-guo has write permissions to this repo, so she would be unable to merge her own). |
I believe @andrew-m-leonard is doing the m2 builds at the moment so I'll merge tomorrow morning when they are done |
run tests |
run tests |
1 similar comment
run tests |
PR TESTER RESULT ❎ Some pipelines failed or the job was aborted! ❎ |
I would merge but it appears I do not have write access to this repo anymore since it was changed to adoptium :( |
@M-Davies - you are listed as a committer (https://projects.eclipse.org/proposals/eclipse-temurin) which means you should have write permissions, so please check your Eclipse profile (and make sure that your github ID is listed in it... you can see it in social media section when you click Edit profile). |
Looks like it's there: https://projects.eclipse.org/user/15355 That is rather strange? |
I'll try and sort it out on slack to avoid the spam here |
I've sent a note to emo team (& cc-ed @M-Davies ) - I think what happened is that Morgan was on the committer list for the Temurin project proposal, but not in the list for the actual project once the proposal was approved. Vague recollection of Wayne not receiving Morgan's email in time for project creation. It can and should be added now, and that is what is requested by the email to emo team. |
Enable all functional and sanity.external for CRIU nightly
Close #83
Signed-off-by: Sophia Guo sophia.gwf@gmail.com