yaydn@protonmail.com wrote:
> På lørdag 4. juli 2026 kl. 16:42, skrev Chris Billington
> <emulti@disroot.org>:
> 
>> Chris Billington wrote:
>>> yaydn@protonmail.com wrote:
<snip>
>> After enabling test debugging with MODCARGO_TEST_ARGS = -- --no-capture,
>> I found the webxdc tests initiate a download of
>> https://apps.testrun.org/webxdc-editor-v3.2.0.xdc
>>
>> Network access is specifically blocked for the _pbuild user in pf.conf
>>
>> After temporarily allowing access to the _pbuild user tests complete
>> with 1 failure:
>>
>> failures:
>>       tools::tools_tests::test_maybe_warn_on_outdated
>>
>> test result: FAILED. 1085 passed; 1 failed; 1 ignored; 0 measured; 0
>> filtered out; finished in 214.78s
>>
>> test_maybe_warn_on_outdated is to check if the DC library is an old
>> version. It is a time-based test, comparing release timestamp and
>> timestamp_now.
>> Initial log contains a warning that a failure may be a false positive
>> due to multi threading, but on a rerun with
>> MODCARGO_TEST_ARGS = -- --no-capture --test-threads 1
>> it still fails.
>>
>> thread 'tools::tools_tests::test_maybe_warn_on_outdated' (298851)
>> panicked at src/tools/tools_tests.rs:453:5:
>> assertion `left == right` failed
>>     left: 1
>>    right: 0
>>
>> 452    let chats = Chatlist::try_load(&t, 0, None, None).await.unwrap();
>> 453    assert_eq!(chats.len(), 0);
>>
>> Probably not catastrophic.
>>
>> However, since network access during port build is not allowed,
>> MODCARGO_TEST=no is appropriate.
>>
>> Regards
>> Chris
>>
>>
> 
> 
> I wasn't sure if that was the expected behaviour before. That makes
> sense to turn off tests for now as they need network.
> 
> When uncommenting, I still get stuck at the same point as prior, but
> I reckon unless there is anything really dire, this can probably go in
> the cvs tree and do any needed changes from there.
> 
> Parla has run for me in the background for a day or two. Unless people
> want to trade test email/invite-links to test accounts I think getting
> feedback from people using this after doing a standard pkg_add would
> be best.
> 
> We can always unlink the packages before 8.0-stable if anything is
> catastrophic breaking under the hood?
> 
> Those using 7.9-stable can still build this for themselves.(stable
> usually only takes security updates after release I think?)
> 
> I'd say ship it aside from the aforementioned space/tab nits. I know not
> what others will opinion.
> 
> Hope this helps. Thanks for porting these packages by the way.
> --
> yaydn
> 

Thanks! To run tests successfully, it would be necessary to temporarily 
comment the block rule for _pbuild in /etc/pf.conf and reload pf rules.

The .tgz files for deltachat-rpc-server and parla are attached.
I have left in a commented MODCARGO_ENV for deltachat-rpc-server that 
forces system sqlcipher in case anyone wants to build on 
7.9-stable/-release. It's not needed on -current.

Is anyone willing to import, or provide OKs?

Regards
Chris Billington

• deltachat-rpc-server.tgz (48K)
• parla.tgz (1K)