bleedingdeacons / monitor / 33535890171
93%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 16
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 92.465% (+0.04%) from 92.422%
33535890171

push

github

web-flow 
feat(alerts): replace on/off duty with an in-meeting mode (#43)

* perf(android): unlock -t:Run and Fast Deployment for the debug loop

Getting a one-line change onto a handset took over two minutes. It now
takes eight seconds.

HandAndroidOnly now sets the SINGULAR TargetFramework, and that one word
is the whole change. With TargetFrameworks plural - even holding a single
value - MSBuild does an outer, dispatching build, and the targets that
deploy to a device do not exist there:

  error MSB4057: The target "Run" does not exist in the project

So the only route to a handset was to build an APK and push it with `adb
install`, which in turn needs EmbedAssembliesIntoApk=true - because the
default, Fast Deployment, deliberately leaves the managed assemblies out
of the APK and expects MSBuild's own Install target to push them
separately. Skip that and the app installs, launches, and aborts with "No
assemblies found in .../.__override__".

Singular restores -t:Run, which builds, installs and launches in one step
and uses Fast Deployment. Measured on the same one-line edit:

  adb install, both ABIs      2m06 + 12s install, 95MB apk
  adb install, arm64 only     1m07 +  9s install, 53MB apk
  -t:Run, Fast Deployment          8s total,      15MB apk

Verified end to end rather than by stopwatch alone: an edit changing the
duty screen's status line to "FASTDEPLOY PROOF" was on the handset's
screen eight seconds later, read back off the device.

This is NOT the -f trap the comment above warns about. That sets
TargetFramework as a global property and forces this TFM onto the plain
net10.0 projects this one references. This is a project-level property
inside this csproj and says nothing about anybody else - the Windows head
and the test project both still build.

An earlier attempt at this appeared to fail with a wall of APT2260
resource errors. That was stale intermediates from the plural layout, not
the change: with obj cleaned first it builds clean every tim... (continued)

1313 of 1420 relevant lines covered (92.46%)

1332.54 hits per line

Coverage Regressions

Lines Coverage ∆ File
9
95.96
0.07% Services/AlertService.cs
Jobs
ID Job ID Ran Files Coverage
1 33535890171.1 16
92.46
GitHub Action Run
Source Files on build 33535890171