Page MenuHomePhabricator

[CI] Clean on failure for Emscripten pipeline
Changes PlannedPublic

Authored by kamil on Mar 5 2024, 4:08 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, May 8, 1:26 PM
Unknown Object (File)
Thu, Apr 25, 1:02 PM
Unknown Object (File)
Thu, Apr 25, 1:02 PM
Unknown Object (File)
Thu, Apr 25, 1:02 PM
Unknown Object (File)
Thu, Apr 25, 1:02 PM
Unknown Object (File)
Thu, Apr 25, 1:02 PM
Unknown Object (File)
Thu, Apr 25, 1:02 PM
Unknown Object (File)
Mon, Apr 22, 2:20 AM
Subscribers

Details

Reviewers
michal
atul
Summary

Potential fix for ENG-7092.
Context in ENG-6977 and ENG-6879.

Now this pipeline has two steps:
Emscripten build - build WASM and compare
Clean on failure and Emscripten build - cleans all caches, builds, and compares again

Test Plan

Tested on CI:

  1. Make sure Clean on failure and Emscripten build cleans only when step Emscripten build fails
  2. Make sure Clean on failure and Emscripten build actually cleans files (looked at logs)
  3. On Emscripten build success Clean on failure and Emscripten build should not perform any actions

Diff Detail

Repository
rCOMM Comm
Branch
clean-on-failure
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

kamil held this revision as a draft.
kamil published this revision for review.Mar 5 2024, 5:32 AM
kamil edited the summary of this revision. (Show Details)
kamil edited the test plan for this revision. (Show Details)
kamil added a reviewer: atul. kamil added 1 blocking reviewer(s): michal.
.buildkite/emscripten.yml
19–20

According to the docs, continue_on_failure: true won't change the status of the build, so event if this succeeds I think the build will still fail?

So that means that build-db-wasm and git diff lines aren't really needed here if I understand it correctly.

Will run on the MacBook Air (where it was previously failing) here: https://phab.comm.dev/D11245